Skip to content

Release/899.0.0#8369

Merged
zone-live merged 2 commits intomainfrom
release/899.0.0
Apr 2, 2026
Merged

Release/899.0.0#8369
zone-live merged 2 commits intomainfrom
release/899.0.0

Conversation

@zone-live
Copy link
Copy Markdown
Contributor

@zone-live zone-live commented Apr 2, 2026

Explanation

Releases social-controller: #8337

References

Checklist

  • I've updated the test suite for new or updated code as appropriate
  • I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
  • I've communicated my changes to consumers by updating changelogs for packages I've changed
  • I've introduced breaking changes in this PR and have prepared draft pull requests for clients and consumer packages to resolve them

Note

Low Risk
Release metadata only (version/changelog updates) with no functional code changes. Low risk aside from potential publishing/versioning mishaps.

Overview
Prepares the 899.0.0 release by bumping the root monorepo version.

Publishes @metamask/social-controllers as 0.1.0 by updating its package version and finalizing the changelog with a 0.1.0 section and correct compare/release links.

Written by Cursor Bugbot for commit 1741952. This will update automatically on new commits. Configure here.

@zone-live zone-live requested review from a team as code owners April 2, 2026 13:17
@zone-live zone-live added this pull request to the merge queue Apr 2, 2026
Merged via the queue into main with commit 150a6ff Apr 2, 2026
336 checks passed
@zone-live zone-live deleted the release/899.0.0 branch April 2, 2026 13:28
micaelae pushed a commit that referenced this pull request Apr 7, 2026
## Explanation

Releases social-controller: #8337

## References

<!--
Are there any issues that this pull request is tied to?
Are there other links that reviewers should consult to understand these
changes better?
Are there client or consumer pull requests to adopt any breaking
changes?

For example:

* Fixes #12345
* Related to #67890
-->

## Checklist

- [ ] I've updated the test suite for new or updated code as appropriate
- [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or
updated code as appropriate
- [ ] I've communicated my changes to consumers by [updating changelogs
for packages I've
changed](https://github.com/MetaMask/core/tree/main/docs/processes/updating-changelogs.md)
- [ ] I've introduced [breaking
changes](https://github.com/MetaMask/core/tree/main/docs/processes/breaking-changes.md)
in this PR and have prepared draft pull requests for clients and
consumer packages to resolve them

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> **Low Risk**
> Release metadata only (version/changelog updates) with no functional
code changes. Low risk aside from potential publishing/versioning
mishaps.
> 
> **Overview**
> Prepares the `899.0.0` release by bumping the root monorepo version.
> 
> Publishes `@metamask/social-controllers` as `0.1.0` by updating its
package version and finalizing the changelog with a `0.1.0` section and
correct compare/release links.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
1741952. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants